Use the figures as base wage estimates. From an employer’s perspective, “labor cost” is often broader than wages. The U.S. Bureau of Labor Statistics, for example, separates wages and salaries from benefit costs when measuring employer compensation. A project budget should add the costs that actually apply.
From a worker’s perspective, the result is gross pay before deductions and tax. It is not take-home pay. A contract may also specify overtime, holiday rates, minimum paid hours or different rates for different tasks.
If the estimate is for a team, calculate each pay band separately and add the results. Multiplying one average rate by all hours can hide meaningful differences, especially when senior staff, contractors and overtime hours have different prices.
Planning a variable schedule: suppose 30 hours are paid at 25 and 10 hours at an overtime rate of 37.50. Calculate 30 × 25 = 750 and 10 × 37.50 = 375, then add them for 1,125. Entering all 40 hours at 25 would miss the premium. The same separate-line approach works for workers with different pay rates.
For a project, distinguish productive hours from paid hours. Meetings, training, setup, travel and paid leave may be real labor costs even when they are not charged directly to one task. Conversely, multiplying a full-year wage by every employee can overstate a short contract. State the period, headcount and included cost categories next to the result so another reader can rebuild the estimate.
